home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Explosion
/
Software Explosion (Fore-Matt Home Computing)(1996).iso
/
system
/
parbench31.lha
/
ParBENCH
/
DocFiles
/
ParBENCH.DOC
< prev
next >
Wrap
Text File
|
1992-12-17
|
14KB
|
329 lines
*****************************************************************
* ParBench ParNET Installation Scripts Disk *
* V3.0 *
* ⌐1992 By Vernon Graner *
*****************************************************************
***Background***
This disk was born out of frustration when I tried to install what
appeared to be a rather simple program from Software Distillery.
After wrestling with the DOCs for a couple of hours and FINALLY
getting all the MountLists and C: commands in the right places, I had
a working ParNET installed. I then decided that for some users, the
install would be almost impossible without some form of simple
installation Icon, so I built one, then another, and so on until I had
a complete collection of ParNET installation scripts.
*** Using This Disk ***
The first step in creating a working ParNET is to READ THE
SOFTWARE DISTILLERY DOCS on how to build the special parallel cable
that is used to connect the two Amigas in the NET. After doing so, TURN
THE POWER OFF ON BOTH AMIGAS and then connect the cable between them.
(Rumor has it that Software Distillery has a financial interest in the
8520 VIA Chip factory, but *I* don't believe it! ;) ) After switching on both
Amigas, all that's left to do is run the scripts on this disk.
**** 2 Amigas With Hard Disks ****
**** Installation Step by Step ****
To get a working PARBench between the 2 Amiga with hard drives:
1. TURN THE POWER OFF on BOTH MACHINES, then connect the special
ParNET Cable between the 2 parallel ports.
2. Boot both machines normally
3. Choose one Amiga to be designated the 'Host' and one Amiga
to be designated 'Client' (It makes no difference which ones)
4. Insert the PARBench disk into the 'Host' Amiga.
5. Doubleclick the 'Install.ParNET' icon.
6. When the script is finished, remove the PARBench disk and
place it in the 'Client' Amiga .
7. Doubleclick the 'Install.ParNET' icon.
ParNET is now installed and ready to run on both machines.
Now all you need to do is start ParNET by opening the ParNET drawer
on your SYS: partition on the HOST machine and double clicking on the
'Boot.Host' icon. Do the same with the client machine with its 'Boot.Client'
icon. If all is working properly, the two machines should post drive lists
for each other, then negotiate a connection. At this point, a disk icon
labled NET should appear on both machines. If this is not the case, then
check the trouble-shooting guide at the end of this document.
The next step is to edit a file that PARBench has created called
'PARNet-DriveList' located in the S: directory of both machines. Due to a
limitation of ParNET, no drives will be visible on either machine until
they have been 'Touched' or CD'd to. This file will be copied to the RAM
disk so that on starting PARNET each Amiga will know what drives are to
be 'touched' on the remote Amiga. The list has a series of drives in it
and you should uncomment the drives you expect to be available at all
times. To uncomment, simply remove the semi-colon before the name of
each drive available on your system. Since there is no way to be certain
that a disk will be in the drive at the time of boot, Floppy Drives are
usually commented out.
The last step in the installation is to use the 'Add.Icons'
script to make the special 'Node.rinfo' files that ParNET requires for icons.
To install icons on the drives you want to appear on the remote machine,
single-click the 'Add.Icons' icon, then hold down the shift key and
double-click on the drive you would like an icon copied to. For example,
I usually would add an icon to the sys: partition of my A3000 by clicking
once on the 'Add.Icons' icon then hold the shift key and click twice on
the WB_2.x icon on the workbench. The script will check for the existence
of a previously installed icon and ask for permission to overwrite if one
is found.
*** Other possible setups: ***
*** When only 1 Amiga has a Hard Disk ***
In this example setup, you could use an A2000HD as a host and an
A500 with no hard drive as a Client. To do so, you would connect the
cable, boot the A2000HD normally and then insert the ParBENCH disk into
the A2000HD's drive. Now you would click the Install.Host Icon and
answer the questions, and then wait for it to finish. Then you would insert
the ParBENCH disk into the A500 and reboot it. While the A500 is rebooting,
open the ParNET drawer on the A2000HD's SYS: partition and click the
Boot.Host icon.
In a moment, the A500 will boot from the ParBENCH disk. You would then
open the A500's floppy drive, open the ParNET Drawer and double click the
Boot.Client script. A Connection should be established between the 2 machines.
By using the provided DefSysDisk icon, you can tell the A500 to utilize the
A2000HD's hard drive as the A500's system partition. To use DefSysDisk, first
double click the Network icon on the A500's screen and look for the SYS icon.
Next single click the DefSysDisk icon, press and hold the shift key and then
double click the SYS icon in the Network drawer. That icon will now become
the system partition for the A500. The A500 may then use the Host A2000HD,
its workbench or even its Startup-sequence. If you like, you can create a
script in the S: directory of the Host Machine (A2000HD in this case) for the
client machine to find and boot from.
The only case where this would not work would be if the Host
machine uses Version 2.04 of Workbench and if the Client machine used V1.3
Kickstart and had no hard drive of its own. In this case using the SYS:
partition on the Host machine will fail because WB2.04 commands REQUIRE a
2.04 kickstart to function.
*** Other possible setups: ***
*** Using a CDTV as an Intelligent CDROM Drive ***
The ParBENCH software package may be used to connect a CDTV to
an Amiga as a CDROM drive By using the HyperMedia Concepts Fred Fish Collection
on CDROM. Here are the step by step instructions:
1. TURN THE POWER OFF on BOTH MACHINES, then connect the special
ParNET Cable between the 2 parallel ports.
2. Insert the Fred Fish CDROM into a caddy and then into the CDTV.
3. Power up both machines and allow them to boot normally.
4. Insert the PARBench disk into the Amiga.
5. Doubleclick the 'Install.ParNET' icon.
6. When the script is finished, remove the PARBench disk.
7. Open the Workbench partition on the Amiga and then open the ParNET drawer.
8. Double click the CDTV.Connect icon.
9. Use the remote on the CDTV to open the Fred Fish Collection icon.
10.Double click the PARNET_SWITCH icon.
The two machines should negotiate a connection and the network icon should
appear on the Workbench screen of the Amiga. Inside of this icon will be the
the RAM DISK icon as well an icon (shaped like a fish tank) for the CD.
******* Activating CDTV NETKEYS ********
If you don't have a keyboard or mouse for your CDTV or if you just don't have
the room or inclination to clutter your desk with 2 keyboards and/or mice, then
NETKEYs is for you! There are only 2 steps to making your Amiga's keyboard and
mouse operate your CDTV:
1. Open the RAM DISK icon on the CDTV, then locate and double-click
the "CDTV.NetKeys" Icon.
2. Open the ParNET Drawer on your Amiga Workbench and double-click
the "Run.NetKeys" Icon.
Now to swap your keyboard/mouse between the Amiga & CDTV hold the left Amiga
key and then press the letter"P". That's all there is to it! (Lots easier to
mouse around this way than to futz with that IR Controller eh?)
******** Conclusion ********
That about wraps it up for ParBENCH instructions. Any questions can be
directed to me or to Software Distillery as I have included their entire
distribution on this disk.
Vernon Graner
Regional Product Specialist
Commodore Business Machines
(512)-288-2515 VOICE
*** History of changes ***
1.0 First release
1.1 Fixed Bugs in the Client Install script.
1.2 Changed the script names to more conventional "Host" & "Client"
from "Server" and Client. Hopefully less Confusing!
1.3-1.9 Small improvements to the scripts including error checking
syntax and echo commands to inform the user.
2.0 Added remove Icons for people that requested and also fixed bugs
in protection system to prevent people from removing the ParNET
from the install disk!!
2.5 A number of changes:
a..Workbench 2.0 drawers used
a..Create a ParNET-Drivelist to
Mount Icons Automatically.
c..Added a Monitor.NET Icon to Utilize the NetSTAT Command
d..Added an 'Add Icons' Icon to shift-click on new drives
in order to easily add ParNET Icons to them.
e..Boot a non-hard drive Amiga client
from a Host Amiga Drive using S:Startup-ParNET
3.0 Added 030 version of the handler for hackers and updated
Documentation for CBM Release.
3.0a Fixed small bug in the ToolTypes of the documentation icon.
3.1 Another Major change up:
a..Reworked the entire scripting mechanism to utilize Commodore's
INSTALLER utility. (I (hate) Parens(!))
b..Combined the Install.Host and Install.Client scripts
c..Relocated most of the icons for easier novice use.
d..Created a special boot icon for connecting to the CDTV and
the Hypermedia Concepts CDROM
e..Reworked the documentation
**** Known Bugs ****
1. "Unknown Command Key "" "
Sometimes when a system is using ARP instead of the standard AmigaDOS,
this error is returned. Solution? Don't use ARP! :>
2. "Could not get information for
object not found"
When a network is established between the CDTV and an Amiga equipped
with AmigaDOS V2.0-2.1, the networked devices will not respond to a DIR nor
will they respond to a LIST command. A Public Domain command like LS
works well in place of the AmigaDOS command. (The PD LS Command
is supplied in the C: directory of this disk.)
3. "CDTV Reboots when I eject my CD"
Unfortunatly, whenever you boot the CDTV from a CDROM, ejecting
that disk will cause the machine to reset. This is a "Feature"
Of the CDTV Operating system and not related to ParNET. The only
solution I have found thus far is to boot the CDTV from a floppy
disk (this one is a good choice!) and THEN change out CDROMs at
will. At this time I know of no other way. :(
PS: LEGAL NOTICE- *I* am not responsible for you blowing up your Amiga,
or your getting divorced by spending too much time playing with ParNET
or anything else like that! I made these scripts to be a service to other
ParNET'ers and that's the end of it. No Guarantees. Void where Prohibited.
All rights deserved. Oh Yeah, the scripts ARE Copyrighted so don't rip
um'... just distribute um! (And DON'T charge people for um ok? Thanx.)
Also, special thanks to Don Pope for bug fixes and Ben Owen of Creative
Imagery for some cool icons! Also, an extra special thanks to John DiLullo.
**** Troubleshooting Guide: ****
Here are a few things that seem to crop up:
Problem: Solution:
-------------------------------------------------------------------------------
INSERT VOLUME PARBENCH IN ANY DRIVE --------Make sure the floppy disk
containing the ParBENCH
scripts is labeled PARBENCH
As all the scripts make
reference to this name!
Unknown Command '.KEY' --------Looks like you have ARP
installed. I don't know a
work around for this one
'cept DON'T USE ARP. :>
INSERT VOLUME NET: IN ANY DRIVE --------The ParNET install most
likely could not find all
the files needed. Try a
Remove.NET and then re-
install.
Could not get information for --------Use the PD command LS located
object not found in the C: directory in place
of the AmigaDOS DIR or LIST.
-------------------------------------------------------------------------------
I CAN'T MAKE IT WORK!
In my experience, the most common reason for a ParNET to fail is an
incorrectly assembled cable or a blown 8520 chip.
The 8520 chip (versatile interface adaptor or VIA) is VERY fragile. If you
plug the cable in with the power on or run the cable thru an A/B box that
is make-before-break or if you plug in an extremely long parnet cable that
has been coiled up on a wool rug in the fall, the 8520 chip may blow up.
If it does, your printer will most likely also cease to function when
connected to that port.
The Amiga has two 8520 chips that control floppy drive access, printing,
mouse, joystick and other things. The bad news is that it has very little
protection built in and will rarely survive even one "oops". The good news
is that most of the time it is a socketed chip and should be replaceable
for less than $50 (alot cheaper if you do it yourself). I have managed to
destroy about four of them in the time I have been ParNETing (about 2 years now)
and most of them were from silly mistakes, like a cable built wrong or
connecting the cable with the power on. One way to diagnose the 8520 is to
swap the two of them inside your machine. If ParNET starts to work but your
mouse or floppy quits, then you've got a blown 8520.
If you still have questions, you can call me voice and I'll be happy to help
you set up a ParNET of your own. (If you are calling long distance and I'm not
here, just leave a message and I'll call you back but I'll have to call
collect!)